O. Levin Internet Draft

Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026 except that the right to produce derivative works is not (automatically) granted. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at 1. Abstract H.323 Specification [3] and H.225.0 [4] together define a system and a set of protocols for multimedia communications services over Packet Based Networks (PBN). H.225.0 [4] messages define means for carrying any standard URL (Uniform Resource Locators) in order to specify source and destination, involved in the call. Starting from H.323v.4, H.323 URL is defined in order to specify H.323 party involved in the call. This H323-URL definition has a form of user@host where user corresponds to endpoint's alias and host corresponds to its domain/zone/gatekeeper (in terms of [3]). The purpose of this document is to register the specified (and presented below) H.323 URL scheme within IANA. This will allow for improved resources use and integration over the Internet. 2. Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [1]. 3. URL scheme name Taking into consideration the guidelines of RFC-2717[12], the proposal is to register the H.323 URL scheme, named "H323", within the IETF tree. It is despite the fact, that H.323 has been defined by ITU-T. H.323 has been widely deployed today and is used side-by-side with other Internet protocols and technologies. We would like to prevent the segmentation of URL scheme definitions, belonging to the same group of applications and running on the same Networks. In addition, it would allow for closer rev ision of the H323 scheme within the IETF community. 4. URL scheme formal syntax definition and character encoding